feat: add agent-orchestrator to community extension catalog#2236
feat: add agent-orchestrator to community extension catalog#2236pragya247 wants to merge 1 commit intogithub:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new built-in Spec Kit extension (“Intelligent Agent Orchestrator”) that scaffolds a discover → index → match → route workflow via extension manifest, config template, and command markdown instructions.
Changes:
- Introduces the
orchestratorextension manifest with commands + hook + default config. - Adds a config template for routing/discovery behavior.
- Adds three new command markdown files (
index,route,discover) plus extension README documentation.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| extensions/orchestrator/extension.yml | Defines the extension (commands, config template, hooks, tags, defaults). |
| extensions/orchestrator/config-template.yml | Provides user-editable routing + discovery configuration template. |
| extensions/orchestrator/commands/speckit.orchestrator.route.md | Documents prompt-to-command routing behavior and expected output. |
| extensions/orchestrator/commands/speckit.orchestrator.index.md | Documents building a unified capability index across sources. |
| extensions/orchestrator/commands/speckit.orchestrator.discover.md | Documents cross-repo scanning for agent/capability sources. |
| extensions/orchestrator/README.md | User-facing overview, install steps, configuration, and roadmap. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Adds a new orchestrator Spec Kit extension scaffold intended to provide cross-catalog capability indexing, prompt-to-command routing, and cross-repo agent discovery via new extension commands.
Changes:
- Adds
extensions/orchestrator/extension.ymlmanifest with three newspeckit.orchestrator.*commands and a proposed init-time hook. - Adds orchestrator configuration template (
config-template.yml) and user-facing docs (README.md). - Adds three command instruction markdown files implementing the discover → index → route workflow as agent-executable specs.
Show a summary per file
| File | Description |
|---|---|
| extensions/orchestrator/extension.yml | Declares the new extension, its commands, config file, hook, tags, and default settings. |
| extensions/orchestrator/config-template.yml | Provides a user-editable config template for routing strategy and cross-repo scanning settings. |
| extensions/orchestrator/commands/speckit.orchestrator.route.md | Defines the agent instructions for scoring and routing user prompts to commands/workflows. |
| extensions/orchestrator/commands/speckit.orchestrator.index.md | Defines the agent instructions for building a unified JSON capability index. |
| extensions/orchestrator/commands/speckit.orchestrator.discover.md | Defines the agent instructions for scanning linked repos/submodules for agent/capability files. |
| extensions/orchestrator/README.md | Documents the extension’s purpose, usage, commands, and configuration. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comments suppressed due to low confidence (2)
extensions/orchestrator/extension.yml:61
- The manifest schema/documentation uses a top-level
defaults:key for default configuration values, notconfig: { defaults: ... }. As written, these defaults are likely to be ignored/misread by tooling and are inconsistent withextensions/template/extension.ymlandextensions/EXTENSION-API-REFERENCE.md. Move these values under a top-leveldefaults:key.
config:
defaults:
matching_strategy: "keyword"
confidence_threshold: 0.5
cross_repo_scan: true
scan_patterns:
- ".agent.md"
- "SKILL.md"
- "AGENTS.md"
- "extension.yml"
- "workflow.yml"
- "preset.yml"
extensions/orchestrator/commands/speckit.orchestrator.route.md:71
- This command describes a fixed weighted scoring algorithm, but the extension config exposes
matching_strategy: "keyword" | "weighted". As written, the config setting has no effect and the docs are internally inconsistent. Update the routing steps sokeyworduses only keyword matching (or document that weights are always applied) and ensure the implementation readsmatching_strategy.
## Step 2: Score Each Capability Against the Prompt
For each capability in the index, compute a relevance score:
1. **Keyword match** (weight: 0.4) — Count how many of the capability's keywords appear in the user prompt
2. **Description match** (weight: 0.3) — Check if words from the user prompt appear in the capability description
3. **Name match** (weight: 0.2) — Check if the capability name is mentioned or closely related
4. **Type bonus** (weight: 0.1) — Prefer workflows > extension commands > core commands for complex prompts; prefer core commands for simple ones
- Files reviewed: 6/6 changed files
- Comments generated: 3
|
Please create it as a community extension as per https://github.com/github/spec-kit/tree/main/extensions |
8c289b1 to
19ce6a7
Compare
There was a problem hiding this comment.
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
There was a problem hiding this comment.
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0 new
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
Comments suppressed due to low confidence (1)
extensions/catalog.community.json:1435
- This catalog already contains an extension with key/id
orchestrator(the existing “Spec Orchestrator” entry). The diff appears to embed that existing entry inside the new one, and even if the JSON were fixed, you can’t publish two extensions with the same catalog key/id. Pick a new unique extension id/key for “Intelligent Agent Orchestrator” (and update README/catalog accordingly), or update the existing entry rather than adding a second one.
"orchestrator": {
"name": "Intelligent Agent Orchestrator",
"id": "orchestrator",
"description": "Cross-catalog agent discovery and intelligent prompt-to-command routing",
"author": "pragya247",
"version": "0.1.0",
"download_url": "https://github.com/pragya247/spec-kit-orchestrator/archive/refs/tags/v0.1.0.zip",
"repository": "https://github.com/pragya247/spec-kit-orchestrator",
"homepage": "https://github.com/pragya247/spec-kit-orchestrator",
"documentation": "https://github.com/pragya247/spec-kit-orchestrator/blob/main/README.md",
"changelog": "https://github.com/pragya247/spec-kit-orchestrator/blob/main/CHANGELOG.md",
"license": "MIT",
"requires": {
"speckit_version": ">=0.6.1"
},
"provides": {
"commands": 3,
"hooks": 1
},
"tags": [
"orchestrator",
"routing",
"discovery",
"agent",
"ai"
"name": "Spec Orchestrator",
"id": "orchestrator",
"description": "Cross-feature orchestration — track state, select tasks, and detect conflicts across parallel specs.",
"author": "Quratulain-bilal",
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
mnriem
left a comment
There was a problem hiding this comment.
Please address Copilot feedback. So cool to see this extension!
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
d327164 to
99a834e
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Register the Intelligent Agent Orchestrator as a community extension. Extension code is hosted externally at: https://github.com/pragya247/spec-kit-orchestrator Changes: - Add agent-orchestrator entry to extensions/catalog.community.json - Add Agent Orchestrator row to README.md community extensions table Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
99a834e to
bbb1bbc
Compare
There was a problem hiding this comment.
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0 new
mnriem
left a comment
There was a problem hiding this comment.
I am so sorry, but it has conflicts again. So many folks are trying to get extensions in the catalog that these PRs get this now. I am working on a way to make this easier! But please in the meanwhile please bear with me and resolve the current conflicts. Thanks!
Summary
Register the Intelligent Agent Orchestrator as a community extension in the spec-kit catalog.
Extension code is hosted externally at: https://github.com/pragya247/spec-kit-orchestrator
What this PR changes
agent-orchestratorentry toextensions/catalog.community.jsonREADME.mdAbout the extension
Cross-catalog agent discovery and intelligent prompt-to-command routing. Provides three commands:
speckit.agent-orchestrator.index— Build a unified catalog indexspeckit.agent-orchestrator.route— Route prompts to the best matching commandspeckit.agent-orchestrator.discover— Discover available agents and capabilitiesRepository: https://github.com/pragya247/spec-kit-orchestrator
Version: 0.1.0
License: MIT